Cloud Architecture Patterns by Bill Wilder

Author:Bill Wilder [Bill Wilder]
Language: eng
Format: epub
Tags: COMPUTERS / Programming / General
ISBN: 9781449319762
Publisher: O'Reilly Media
Published: 2012-09-19T16:00:00+00:00

Impact

Availability, Scalability, User Experience

Mechanics

Use the Busy Signal Pattern to detect and handle normal transient failures that occur when your application (the client in this relationship) accesses a cloud service. A transient failure is a short-lived failure that is not the fault of the client. In fact, if the client reissues the identical request only milliseconds later, it will often succeed.

Transient failures are expected occurrences, not exceptional ones, similar to making a telephone call and getting a busy signal.

Busy Signals Are Normal

Consider making a phone call to a call center where your call will be answered by one of hundreds of agents standing by. Usually your call goes through without any problem, but not every time. Occasionally you get a busy signal. You don’t suspect anything is wrong, you simply hit redial on your phone and usually you get through. This is a transient failure, with an appropriate response: retry.

However, many consecutive busy signals will be an indicator to stop calling for a while, perhaps until later in the day. Further, we only will retry if there is a true busy signal. If we’ve dialed the wrong number or a number that is no longer in service, we do not retry.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.